|
|
|
| TABLE 12.2.CONTINUED | | Form | Field | Button | | frmMaintainUsers (cont.) | Grid of Assigned Workgroups (ID, Name, Description, Department Number, Manager, Assigned Role (if any)) | | | List of workgroups from which to choose a workgroup | | | List of roles from which to choose a role | | | frmMaintainWorkgroups | Workgroup Name | Done | | ID Number | New Workgroup | | Workgroup Status | New Role | | Department Number | Modify Workgroup | | Manager | Modify Role | | List of Users | Delete Workgroup | | List of Roles | Delete Role | | List of Users Assigned to Role | Assign User to Role | | List of Workgroups | Unassign User to Role | | Role Name (for new roles, or to modify existing role names) | |
|
|
|
|
|
|
The events of each of the GUI controls on each form will have corresponding methods in their respective controllers. For standard events based on clicking a text, grid, list, or label control, FormOperations will handle processing them. Examples include maximum length of text (default to 255 characters for some controls), date formatting, and so on. However, if clicking a text, grid, list, or label control requires processing that is not standard, such as autopopulating a list of bank products, the form's controller needs to have a meaningful method to handle this responsibility. If you're imaginative, you might even create helper classes for your controllers so that these controllers don't grow too large. |
|
|
|
|
|